Skip to content

docs: refresh README, add docs index and link checker, fix stale paths#584

Merged
BigSimmo merged 3 commits into
mainfrom
claude/repo-docs-infrastructure-4c2787
Jul 13, 2026
Merged

docs: refresh README, add docs index and link checker, fix stale paths#584
BigSimmo merged 3 commits into
mainfrom
claude/repo-docs-infrastructure-4c2787

Conversation

@BigSimmo

@BigSimmo BigSimmo commented Jul 13, 2026

Copy link
Copy Markdown
Owner

Summary

Documentation and doc-infrastructure refresh, plus a small image-build fix for a main-side regression this PR's CI surfaced.

  • README.md: corrected the verify:cheap chain description (it had drifted from package.json — the chain now includes check:github-actions, brand:check, check:type-scale, check:icon-scale), documented the missing verify:pr-local gate (including the --dry-run --files inspection form), and rewrote the CI paragraph to match the actual risk-scoped ci.yml jobs (changes/static-pr/pr-required aggregate, path-scoped coverage/build/ui-critical/db-reset-verify, gated release-browser-matrix).
  • New docs/README.md: categorized index of all ~85 docs, distinguishing maintained documents from point-in-time records and archive, marking generated files with their update commands. No docs were moved or deleted, so all inbound links keep resolving.
  • docs/agents-guide.md: rewritten as a short non-duplicating pointer to AGENTS.md, docs/codebase-index.md, and the new index, so it can no longer drift from the authoritative agent rules.
  • New scripts/check-docs-links.mjs + npm run docs:check-links: verifies repo-path references in the maintained doc surface resolve. Markdown link targets are resolved relative to the containing file (repo-root-style targets also accepted) and confined to the repository root; docs/redesign/ and docs/superpowers/ are scanned by default while archive/, audit/, and dated point-in-time records stay behind --all (per Codex + CodeRabbit review). Advisory tool only — deliberately not wired into verify:cheap or CI.
  • Stale references the checker found and this PR fixes: phantom favourites-home-page.tsx in the site-map generator route-ownership table (real file is favourites-command-library-page.tsx; docs/site-map.md regenerated), ambiguous supabase/client.tsx-style paths in docs/codebase-index.md (now src/lib/supabase/), and an un-updated link to the archived phase-0 baseline in docs/search-rag-master-context.md.
  • Dockerfile + Dockerfile.worker: copy scripts/install-git-hooks.mjs into the npm ci stages. feat(dx): Wave 1 session guards — retire repeated push-time traps #583 (merged to main after this branch was cut) added it as the npm postinstall hook, so both app-image and worker-image builds failed at npm ci with the module missing. This branch merged origin/main to pick up the script.

Clinical governance preflight

N/A — documentation, an advisory doc-link script, and a Dockerfile dependency-stage COPY only. No ingestion, answer generation, search/ranking, source rendering, document access, privacy, production env, or clinical output changes.

Verification

  • npm run sitemap:update + npm run sitemap:check — green (regenerated map committed)
  • npm run brand:check — green
  • node scripts/check-docs-links.mjs — 760 repo path references resolve on the default surface; --all fails only on historical/dated docs, as designed
  • npx eslint scripts/check-docs-links.mjs scripts/generate-site-map.ts — clean
  • npx vitest run tests/site-map.test.ts — 5/5 passed (re-run after merging main)
  • Prettier run on all changed files

🤖 Generated with Claude Code

- README: correct the verify:cheap chain, document verify:pr-local, and
  rewrite the CI paragraph to match the risk-scoped ci.yml jobs
  (changes/static-pr/pr-required aggregate, gated release-browser-matrix)
- Add docs/README.md: categorized index of all docs distinguishing
  maintained docs from point-in-time records and archive
- Rewrite docs/agents-guide.md as a non-duplicating pointer to AGENTS.md,
  codebase-index, and the new docs index
- Add scripts/check-docs-links.mjs + `npm run docs:check-links` (advisory;
  not wired into verify chains) to catch dead repo-path references
- Fix stale references it found: phantom favourites-home-page.tsx in the
  site-map generator (regenerated docs/site-map.md), ambiguous
  src/lib/supabase paths in codebase-index, archived phase-0 link in
  search-rag-master-context

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@supabase

supabase Bot commented Jul 13, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

Documentation navigation and verification guidance were expanded, a documentation link-checking command was added, onboarding references were updated, and stale module, archive, and site-map paths were synchronized.

Changes

Documentation maintenance

Layer / File(s) Summary
Documentation link validation
scripts/check-docs-links.mjs, package.json
Adds docs:check-links, which scans documentation references, validates repository paths, supports --all, and reports missing targets.
Documentation navigation and verification guidance
README.md, docs/README.md, docs/agents-guide.md, docs/codebase-index.md
Adds the categorized documentation index and link-check instructions, updates verification-gate guidance, and refreshes onboarding and Supabase module references.
Documentation reference synchronization
docs/search-rag-master-context.md, docs/site-map.md, scripts/generate-site-map.ts
Updates the archived baseline path and synchronizes the Favourites source component reference.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related PRs

  • BigSimmo/Database#440: Updates documentation for CI and verification gates, overlapping with this PR’s README verification guidance.
🚥 Pre-merge checks | ✅ 4 | ❌ 7

❌ Failed checks (1 warning, 6 inconclusive)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 70.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Generated And Sensitive Files ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
Verification Claims ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
Risky Git Or Deployment Actions ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
Supabase Project And Schema Safety ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
Runtime And Package Manager Integrity ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
Api Route Failure Handling ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
✅ Passed checks (4 passed)
Check name Status Explanation
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly matches the main doc refresh, new docs index/link checker, and stale path fixes.
Description check ✅ Passed The description is mostly complete and covers summary, verification, and governance context, with only the Notes section left blank.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/repo-docs-infrastructure-4c2787
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch claude/repo-docs-infrastructure-4c2787

Comment @coderabbitai help to get the list of available commands.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0d8b6190c5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread scripts/check-docs-links.mjs Outdated
@github-actions

Copy link
Copy Markdown

@codex resolve actionable Codex review findings for this pull request and current head using the repository instructions. This is the pull request's single automatic repair pass: do not perform a fresh review, create new standalone findings, or request another review. Work only the existing unresolved Codex threads on the current head. Always fix P0 and P1 findings. For P2 and lower findings, fix only clear, scoped, low-risk issues; otherwise disposition them with a concise reason. After fixing or dispositioning a thread, reply in that thread with as the first line, followed by a concise summary; that marker authorizes the workflow to close that exact thread. If human input or new authorization is required, do not use the marker and leave the thread open with the blocker. Finish only after every actionable thread is fixed or dispositioned and closed, or explicitly left open for a human decision. Do not update the branch from main, address unrelated reviews, broaden scope, or create more than one scoped fix commit. Do not use external APIs, paid services, credentials, dependency changes, or broad refactors unless explicitly authorized. Add targeted tests where behavior changes and run the narrowest relevant validation.

@chatgpt-codex-connector

Copy link
Copy Markdown

To use Codex here, create a Codex account and connect to github.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@scripts/check-docs-links.mjs`:
- Around line 76-79: Update the Markdown link handling in the checker’s matchAll
loop to resolve relative targets against the scanned file’s directory, while
preserving root-relative handling. Normalize the resolved path and only validate
candidates whose canonical location remains under repoRoot, rejecting links that
escape the repository; ensure links in docs/README.md and docs/agents-guide.md
are included.
- Around line 54-61: Update the directory traversal around scanAll so maintained
nested documentation directories, including docs/redesign and docs/superpowers,
are scanned by default. Keep dated, audit, and archive directories excluded
unless scanAll is enabled, while preserving the existing Markdown target
collection behavior.
🪄 Autofix (Beta)

❌ Autofix failed (check again to retry)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: adca9ff8-987e-46a6-8d96-f6587e196e3e

📥 Commits

Reviewing files that changed from the base of the PR and between b8b4843 and 0d8b619.

📒 Files selected for processing (9)
  • README.md
  • docs/README.md
  • docs/agents-guide.md
  • docs/codebase-index.md
  • docs/search-rag-master-context.md
  • docs/site-map.md
  • package.json
  • scripts/check-docs-links.mjs
  • scripts/generate-site-map.ts

Comment thread scripts/check-docs-links.mjs Outdated
Comment thread scripts/check-docs-links.mjs Outdated
@BigSimmo
BigSimmo enabled auto-merge (squash) July 13, 2026 13:52
BigSimmo and others added 2 commits July 13, 2026 22:03
…stinstall

- check-docs-links: markdown link targets now resolve relative to the
  containing file (and accept the repo-root-relative convention), are
  confined to the repository root, and docs/redesign + docs/superpowers
  are scanned by default while archive/audit/dated records stay behind
  --all (review findings from Codex and CodeRabbit)
- Dockerfile + Dockerfile.worker: copy scripts/install-git-hooks.mjs into
  the npm ci stages — main's #583 added it as the npm postinstall hook, so
  every image build failed at npm ci with the module missing

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fa75ccbf89

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread README.md
@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Note

Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it.

Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found.

@BigSimmo
BigSimmo merged commit ac0bed9 into main Jul 13, 2026
25 checks passed
@BigSimmo
BigSimmo deleted the claude/repo-docs-infrastructure-4c2787 branch July 14, 2026 11:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant